View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001696 | K18X001.00 SKB SWAN | xTS certification | public | 2023-03-31 17:12 | 2025-04-07 10:20 |
| Reporter | Assigned To | (ALTech) Sangmin Choi | Due Date | ||
| Priority | normal | Severity | s4-minor | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Summary | 0001696: Android 10.0 Security Patch Support | ||||
| Description | Hi Sangmin, According to Google announcement as follows, This is a reminder that security patch support for Q (Android version 10, API level 29) expires on February 28, 2023. In accordance with this policy, the February 2023 Partner Preview security bulletin will be the last one containing fixes for Q (10). Partners who wish to continue supporting security updates on these devices can manually backport security patches themselves and continue to use the applicable patch string. As we know, there is no OS upgrade plan for Synaptics VS550, so we need to backport security patch to ATV10. The Security Patch of current SWAN's code is 2023-02 We can backport security patches from ATV11 from 2023-03, but as you know, some code bases of ATV11 different from ATV10. some Security patches can not be applied to ATV10 by "git am" command. In my opinion, If there are no patch conflicts, we can apply the ATV11 patch to the ATV10, but if we encounter a patch that is not easy to apply, we will ignore it. I think all security patch between all OEMs should be consistent, the behavior of SW will be same, so we would like to know other 2 OEMs plan. After applying security patch, we also need to update security patch string, otherwise we will have following failure, run gts -m GtsOsTestCases -t com.google.android.os.gts.SecurityPatchTest#testSecurityPatchDate Could you let us know other OEMs opinion? Thanks, Jason | ||||
| Tags | No tags attached. | ||||
| Attach Tags | |||||
| User List |
(ALTech) Wooshin Kang , (SW) Jacky Chiang |
|---|
|
|
Hi Sangmin, Wooshin, Could you check it? Thanks, Jason |
|
|
Hi Jason, I have informed to SKB manager about this issue. If i will get any update, I will inform you. Thanks. |
|
|
Hi Wooshin, Any update ? Do you know other manufacturer's plan? Thanks, Jason |
|
|
Hi Jason, I have checked it to SKB Manage but they didn't discuss yet. Thanks. |
|
|
Hi Jason, 1. About OS upgrade, SKB have discussed with Jeff ( google TAM ) and it should be finished within next year. 2. About, applying security patch before OS-upgrade, skb is saying like below. "OEMs have to solve it by them self because owner of getting certification is OEM ." 3. If you encounter below issue when you patch manually, inform me about this. I will inform it to skb and discuss for avoid different behavior of OEM S/W. If there are no patch conflicts, we can apply the ATV11 patch to the ATV10, but if we encounter a patch that is not easy to apply, we will ignore it. I think all security patch between all OEMs should be consistent, the behavior of SW will be same, so we would like to know other 2 OEMs plan. After applying security patch, we also need to update security patch string, otherwise we will have following failure, run gts -m GtsOsTestCases -t com.google.android.os.gts.SecurityPatchTest#testSecurityPatchDate Thanks. |
|
|
Hi Wooshin, 1. Did you get any information from Synaptics for OS upgrade? 2. I'll apply it first, and let you know which patch can not easy to apply. Thanks, Jason |
|
|
Hi Wooshin, Regarding 2022-03 Security Patch, Please discuss it with other OEM Hi Wooshin, Regarding 2022-03 Security Patch ├── external │ └── zlib │ └── 0001-Fix-a-bug-when-getting-a-gzip-header-extra-field-with-inflat.bulletin.patch (Apply manually) ├── frameworks │ ├── base │ │ ├── 0001-DO-NOT-MERGE-Suppress-notifications-when-device-enter-lockdo.bulletin.patch (Already applied 2022-08) │ │ ├── 0002-RESTRICT-AUTOMERGE-Validate-permission-tree-size-on-permissi.bulletin.patch (Apply manually) │ │ ├── 0003-RESTRICT-AUTOMERGE-Revoke-SYSTEM_ALERT_WINDOW-on-upgrade-pas.bulletin.patch (Can not be applied, the code base is too different) │ │ ├── 0004-Fix-sharing-to-another-profile-where-an-app-has-multiple-tar.bulletin.patch (Can not be applied, file not exist) │ │ ├── 0005-Move-service-initialization.bulletin.patch (Apply manually) │ │ ├── 0006-Enable-user-graularity-for-lockdown-mode.bulletin.patch (Apply manually) │ │ ├── 0007-RESTRICT-AUTOMERGE-Revoke-dev-perm-if-app-is-upgrading-to-po.bulletin.patch (Can not be fully applied) │ │ └── 0008-Reconcile-WorkSource-parcel-and-unparcel-code-.bulletin.patch (Can be applied by git am) │ └── opt │ └── net │ └── wifi │ └── 0001--RESTRICT-AUTOMERGE-Only-handle-saveToStore-from-the-WifiNe.bulletin.patch (Can not be applied, functions not exist) ├── packages │ └── apps │ ├── Bluetooth │ │ └── 0001-Fix-URI-check-in-BluetoothOppUtility-java.bulletin.patch (Already applied 2022-12) │ └── Settings │ ├── 0001--DO-NOT-MERGE-FRP-bypass-defense-in-the-settings-app.bulletin.patch (Apply manually) │ └── 0002-Add-DISALLOW_APPS_CONTROL-check-into-uninstall-app-for-all-u.bulletin.patch (Can be applied by git am) └── system └── bt ├── 0001-Report-failure-when-not-able-to-connect-to-AVRCP.bulletin.patch (Already applied 2023-02) ├── 0002-Add-bounds-check-in-avdt_scb_act-cc.bulletin.patch (Already applied 2023-02) ├── 0003-Fix-an-OOB-Write-bug-in-gatt_check_write_long_terminate.bulletin.patch (Can be applied by git am) ├── 0004-Fix-an-OOB-access-bug-in-A2DP_BuildMediaPayloadHeaderSbc.bulletin.patch (Can be applied by git am) └── 0005-Fix-an-OOB-write-in-SDP_AddAttribute.bulletin.patch (Can be applied by git am) Thanks, Jason |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2023-03-31 17:12 |
|
New Issue | |
| 2023-03-31 17:12 |
|
Status | new => assigned |
| 2023-03-31 17:12 |
|
Assigned To | => (ALTech) Sangmin Choi |
| 2023-03-31 17:13 |
|
Issue Monitored: (ALTech) Wooshin Kang | |
| 2023-04-06 09:43 |
|
Note Added: 0012733 | |
| 2023-04-06 10:18 | (ALTech) Wooshin Kang | Note Added: 0012735 | |
| 2023-04-13 09:40 |
|
Note Added: 0012833 | |
| 2023-04-13 12:20 | (ALTech) Wooshin Kang | Note Added: 0012838 | |
| 2023-04-18 13:21 | (ALTech) Wooshin Kang | Note Added: 0012909 | |
| 2023-04-18 13:52 |
|
Issue Monitored: (SW) Jacky Chiang | |
| 2023-04-18 13:55 |
|
Note Added: 0012913 | |
| 2023-04-18 16:58 |
|
Note Added: 0012915 | |
| 2023-04-21 14:04 |
|
Note Edited: 0012915 | |
| 2025-04-07 10:20 | (PM) Sheila Tu | Status | assigned => closed |
| 2025-04-07 10:20 | (PM) Sheila Tu | Resolution | open => fixed |
